@JKamsker is attempting to deploy a commit to the General Action Team on Vercel.

A member of the Team first needs to authorize it.

@codex review

@JKamsker - Your PR looks great! I have one suggestion that would make the PTY spawning even more
robust:

Currently on Unix, when spawning provider terminals, we rely on the shell's PATH to find the CLI:
/bin/zsh -lic "codex; exec /bin/zsh -il"

To make this more reliable (especially for users with non-standard shell configs), we could resolve
the CLI path explicitly first. I've tested a small addition that uses the same path resolution logic
from ConnectionsService.ts:

Add this helper function near the top of ptyManager.ts (around line 15):
function resolveCliPath(command: string): string | null {
const { execFileSync } = require('child_process');
const { extname } = require('node:path');
const resolver = process.platform === 'win32' ? 'where' : 'which';

try {
  const result = execFileSync(resolver, [command], { encoding: 'utf8' });
  const lines = result
    .split(/\r?\n/)
    .map((l) => l.trim())
    .filter(Boolean);

  if (process.platform !== 'win32') {
    return lines[0] ?? null;
  }

  // Windows: prefer executable extensions
  const extensionPreference: Record<string, number> = {
    '.exe': 0,
    '.cmd': 1,
    '.bat': 2,
    '.com': 3,
    '.ps1': 50,
    '': 100,
  };

  const best = [...lines].sort((a, b) => {
    const aExt = extname(a).toLowerCase();
    const bExt = extname(b).toLowerCase();
    const aRank = extensionPreference[aExt] ?? extensionPreference[''];
    const bRank = extensionPreference[bExt] ?? extensionPreference[''];
    return aRank - bRank;
  })[0];

  return best ?? null;
} catch {
  return null;
}

}

Then modify the provider command building (around line 182-189):
// Change from:
const cliCommand = provider.cli || baseLower;
const commandString =
cliArgs.length > 0
? ${cliCommand} ${cliArgs .map((arg) => /[\s'"\\$\n\r\t]/.test(arg) ? '${arg.replace(/'/g, "'\\''")}' : arg
)
.join(' ')}`
: cliCommand;

// To:
const cliCommand = provider.cli || baseLower;
const resolvedCliPath = resolveCliPath(cliCommand);
const finalCommand = resolvedCliPath || cliCommand;
const commandString =
cliArgs.length > 0
? ${finalCommand} ${cliArgs .map((arg) => /[\s'"\\$\n\r\t]/.test(arg) ? '${arg.replace(/'/g, "'\\''")}' : arg
)
.join(' ')}`
: finalCommand;

This would make the provider spawning use absolute paths (e.g.,
/Users/x/.nvm/versions/node/v20/bin/codex) instead of just codex, making it independent of shell
PATH configuration while still falling back to the current behavior if resolution fails.

What do you think? Happy to test this addition if you'd like to include it! The rest of your PR
works great on macOS.

lmk what you think @JKamsker :)

Hey @arnestrickmann, thanks for the quick reply!
I have updated the PR (and it still works for me) - is that what you had in mind?